You might receive a Segmentation Violation when opening a database table in SAS. The SAS® Log contains the error and traceback:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [DATASTEP]
Segmentation Violation
Traceback of the Exception:
/usr/local/SASHome/SASFoundation/9.4/sasexe/sas(+0x16840e) [0x56374b0c740e]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sas(+0x4eddf) [0x56374afadddf]
/usr/local/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x7f80c76edac4]
/usr/lib64/libpthread.so.0(+0xf630) [0x7f80c8d16630]
/usr/local/SASHome/SASFoundation/9.4/sasexe/tkmk.so(skmMemAlloc+0x169) [0x7f80c76ff4d9]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sas(+0x5d8c6) [0x56374afbc8c6]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasiomet(+0x1cbad) [0x7f806d2a2bad]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasiomet(+0x16c96) [0x7f806d29cc96]
/usr/local/SASHome/SASFoundation/9.4/sasexe/tkexml.so(+0x10c00) [0x7f80a6251c00]
/usr/local/SASHome/SASFoundation/9.4/sasexe/tkexml.so(+0xc85d) [0x7f80a624d85d]
/usr/local/SASHome/SASFoundation/9.4/sasexe/tkexml.so(parseElement+0x68c) [0x7f80a624a77c]
/usr/local/SASHome/SASFoundation/9.4/sasexe/tkexml.so(XMLParse+0x33f) [0x7f80a624761f]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasiomet(xml2yoe+0x1a7) [0x7f806d29aae7]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasiomet(metaget+0x2764) [0x7f806d2a7634]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasiomet(yoeopen+0x750) [0x7f806d2908c0]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasyoio(yyoopen+0x2e50) [0x7f808899e7e0]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasyoio(yoopen+0x1f7) [0x7f808899b5b7]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasdsa(dsdbivl+0x26b) [0x7f807c09539b]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasdsc(dscdsio+0x10ec) [0x7f8077744b8c]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasxshel(ysprstm+0xbe2) [0x7f80af591bf2]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasdsc(dsccomp+0x1b4) [0x7f8077739fa4]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sasds(sasds+0x199) [0x7f807c2b6e89]
/usr/local/SASHome/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x56374afad93a]
/usr/lib64/libpthread.so.0(+0x7ea5) [0x7f80c8d0eea5]
/usr/lib64/libc.so.6(clone+0x6d) [0x7f80c82fa8cd]
Client applications might produce additional messages. For example, SAS® Enterprise Guide® might present a message box with the following text:
This issue occurs in two scenarios.
This problem occurs when the table is accessed via the Metadata LIBNAME Engine (META) and the Additional Table Options value in the metadata exceeds 1,024 characters.
Here is an image of the Additional Table Options property for the table using SAS® Management Console:
In this example, leading characters in the DBSASTYPE option were used to make the value easy to read, but are otherwise unimportant to the DBSASTYPE option. These leading spaces add to the character count.
To circumvent the error, reduce the option value to 1,024 or fewer characters.
This problem occurs when the table is accessed via the Metadata LIBNAME Engine (META) and the Additional Table Options in the metadata contains a null value.
This image shows a blank entry field.
The problem arises if you first save a value, and then later backspace over that value. The property is still associated with the table, but it contains no value.
Here is an example of the Property object in the metadata represented in XML. The attribute UseValueOnly="1" tells the software to use the DefaultValue. However, the DefaultValue attribute contains a null value.
To circumvent the error, complete these steps:
A hot fix is planned for this issue.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Metadata Server | Windows 7 Enterprise x64 | 9.4_M6 | 9.4 TS1M6 | ||
Windows 7 Enterprise 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows Server 2019 | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows Server 2016 | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows Server 2012 Std | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows Server 2012 R2 Std | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows Server 2012 R2 Datacenter | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows Server 2012 Datacenter | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 10 | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8.1 Pro x64 | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8.1 Pro 32-bit | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8.1 Enterprise x64 | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8 Pro x64 | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8 Pro 32-bit | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8 Enterprise x64 | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft Windows 8 Enterprise 32-bit | 9.4_M6 | 9.4 TS1M6 | ||||
Microsoft® Windows® for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
z/OS | 9.4_M6 | 9.4 TS1M6 | ||||
Windows 7 Home Premium 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
Windows 7 Home Premium x64 | 9.4_M6 | 9.4 TS1M6 | ||||
Windows 7 Professional 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
Windows 7 Professional x64 | 9.4_M6 | 9.4 TS1M6 | ||||
Windows 7 Ultimate 32 bit | 9.4_M6 | 9.4 TS1M6 | ||||
Windows 7 Ultimate x64 | 9.4_M6 | 9.4 TS1M6 | ||||
64-bit Enabled AIX | 9.4_M6 | 9.4 TS1M6 | ||||
64-bit Enabled Solaris | 9.4_M6 | 9.4 TS1M6 | ||||
HP-UX IPF | 9.4_M6 | 9.4 TS1M6 | ||||
Linux for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
Solaris for x64 | 9.4_M6 | 9.4 TS1M6 |
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2020-08-26 15:39:25 |
Date Created: | 2020-07-29 11:28:18 |